Add SECURITY.md with vulnerability disclosure policy#6
Open
ouwibo wants to merge 1 commit into
Open
Conversation
Establishes a private channel for security reports, a 90-day coordinated disclosure window, and a safe harbor clause for good-faith researchers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi maintainers — I'm @ouwibo (
ouwibo@gmail.com), a security researcher who's been spending time with the ATXP stack.Because ATXP touches wallets, identity, and live payment rails, I noticed the repo doesn't yet have a
SECURITY.mdand there's no obvious private channel for researchers to report issues responsibly. This PR adds a standard policy so that any future findings — from this community or from your own users — have a clear path that isn't a public issue.What this PR does
SECURITY.mdto the repo root.security@atxp.aias the preferred contact, withsupport@atxp.aias fallback (since I couldn't find asecurity@listed anywhere).Why now
Live USDC on the payment path means real money exposure if anything in routing / custody / signing has an edge case. Having a published policy:
I tried to keep the wording neutral and template-friendly — feel free to edit the contact addresses, scope, or timelines to match how the team actually wants to operate. Happy to iterate on this in review.
I'd also like to coordinate privately on a sensitive finding I have. Please reach me at
ouwibo@gmail.comor DM @ouwibo.— @ouwibo